Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add stale issues Github Actions Workflow #5342

Merged
merged 2 commits into from
Jun 5, 2024
Merged

Add stale issues Github Actions Workflow #5342

merged 2 commits into from
Jun 5, 2024

Conversation

sisco0
Copy link
Contributor

@sisco0 sisco0 commented Jun 5, 2024 •
edited
Loading

  • Because this PR includes a bug fix, relevant tests have been included.
  • Because this PR includes a new feature, the change was previously discussed on an Issue or with someone from the team.
  • I didn't do anything of this.

Solves #5306.

This pull request introduces a GitHub Actions workflow that automatically closes issues labeled with status:needs-more-info if there has been no follow-up for a specified period of time. This helps maintain a clean and manageable issue tracker by closing inactive support cases that require additional information from the reporter.

Following considerations are had for the current implementation:

  1. The workflow runs daily at midnight UTC to check for stale issues
  2. The workflow can also be triggered manually from the GitHub Actions tab using the workflow_dispatch event
  3. Issues labeled with status:needs-more-info will be marked as stale after 7 days of inactivity
  4. Once marked as stale, the issue will be automatically closed after an additional 7 days if there is still no activity
  5. Exemption: Issues labeled with status:do-not-close will be exempt from being marked as stale and closed automatically

No testing has been performed over the current implementation.
The https://github.com/actions/stale repository examples were used for designing the current Github Action Workflow.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Jun 5, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: 3bb6376

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel Vercel
Copy link

vercel bot commented Jun 5, 2024 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
hardhat ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 5, 2024 7:45pm

@sisco0 sisco0 marked this pull request as ready for review June 5, 2024 16:09
@alcuadrado alcuadrado added the no changeset needed This PR doesn't require a changeset label Jun 5, 2024
@alcuadrado
Copy link
Member

Thanks!

@alcuadrado alcuadrado merged commit bdd04d3 into NomicFoundation:main Jun 5, 2024
6 of 7 checks passed
@alcuadrado
Copy link
Member

I just tested this manually

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@alcuadrado alcuadrado alcuadrado approved these changes

Assignees

@kanej kanej

Labels
no changeset needed This PR doesn't require a changeset status:triaging
Projects
Hardhat
Archived in project
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@sisco0 @alcuadrado @kanej